home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Performance Co-Pilot 1.3
/
SGI Performance Co-Pilot 1.3.iso
/
dist
/
pcp.idb
/
usr
/
share
/
catman
/
u_man
/
cat1
/
pmlogmerge.z
/
pmlogmerge
Wrap
Text File
|
1997-04-03
|
6KB
|
133 lines
PPPPMMMMLLLLOOOOGGGGMMMMEEEERRRRGGGGEEEE((((1111)))) PPPPMMMMLLLLOOOOGGGGMMMMEEEERRRRGGGGEEEE((((1111))))
NNNNAAAAMMMMEEEE
ppppmmmmllllooooggggmmmmeeeerrrrggggeeee - concatenate and merge Performance Co-Pilot archive logs
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
////uuuussssrrrr////ppppccccpppp////bbbbiiiinnnn////ppppmmmmllllooooggggmmmmeeeerrrrggggeeee [----ssss _s_a_m_p_l_e_s] [----SSSS _t_i_m_e] [----TTTT _t_i_m_e] [----vvvv _v_o_l_s_a_m_p_l_e_s]
_i_n_p_u_t [...] _o_u_t_p_u_t
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
ppppmmmmllllooooggggmmmmeeeerrrrggggeeee operates upon archive logs of performance metric values that
may be ``played back'' by other Performance Co-Pilot (PCP) tools. These
logs form the basis of the VCR paradigm and retrospective performance
analysis services common to the PCP toolkit.
Like ccccaaaatttt(1), ppppmmmmllllooooggggmmmmeeeerrrrggggeeee accepts one or more PCP archives named via the
_i_n_p_u_t arguments, and produces a single PCP archive with _o_u_t_p_u_t as the
base name for the physical files that constitute an archive log.
All of the _i_n_p_u_t archives must have been collected from the same host.
Without any arguments, ppppmmmmllllooooggggmmmmeeeerrrrggggeeee uses the timestamps associated with
each record in an archive to merge all of _i_n_p_u_t archives into a single
_o_u_t_p_u_t archive with all records in their correct chronological sequence.
If the _i_n_p_u_t archives were created over disjoint time intervals, this
process is equivalent to concatenating the archives in the correct
temporal sequence.
CCCCOOOOMMMMMMMMAAAANNNNDDDD LLLLIIIINNNNEEEE OOOOPPPPTTTTIIIIOOOONNNNSSSS
The command line options ----SSSS and ----TTTT control the overall start and end time
for the resultant merged archive, allowing one to clip the merge to a
window of time. These options are common to most Performance Co-Pilot
tools and are fully described in ppppmmmmPPPPaaaarrrrsssseeeeTTTTiiiimmmmeeeeWWWWiiiinnnnddddoooowwww(3). The other time
window options, ----AAAA and ----OOOO, are not applicable in this context and are not
supported.
The other available options are:
----ssss Force the merge to terminate after _s_a_m_p_l_e_s log records have been
written. This will override the ----TTTT option if it occurs sooner.
----vvvv The _o_u_t_p_u_t archive is potentially a multi-volume data set, and the
----vvvv option causes ppppmmmmllllooooggggmmmmeeeerrrrggggeeee to start a new volume after _v_o_l_s_a_m_p_l_e_s
log records have been written to the archive.
FFFFIIIILLLLEEEESSSS
For each of the _i_n_p_u_t and _o_u_t_p_u_t archives, several physical files are
used.
_a_r_c_h_i_v_e....mmmmeeeettttaaaa metadata (metric descriptions, instance domains,
etc.) for the archive log
_a_r_c_h_i_v_e....0000 initial volume of metrics values (subsequent volumes
have suffixes 1111, 2222, ...)
PPPPaaaaggggeeee 1111
PPPPMMMMLLLLOOOOGGGGMMMMEEEERRRRGGGGEEEE((((1111)))) PPPPMMMMLLLLOOOOGGGGMMMMEEEERRRRGGGGEEEE((((1111))))
_a_r_c_h_i_v_e....iiiinnnnddddeeeexxxx temporal index to support rapid random access to the
other files in the archive log
SSSSEEEEEEEE AAAALLLLSSSSOOOO
ppppmmmmdddduuuummmmpppplllloooogggg(1), ppppmmmmllllcccc(1), ppppmmmmllllooooggggggggeeeerrrr(1), and PPPPMMMMAAAAPPPPIIII(3).
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
All error conditions detected by ppppmmmmllllooooggggmmmmeeeerrrrggggeeee are reported on _s_t_d_e_r_r with
textual (if sometimes terse) explanation.
Should one of the input archive logs be corrupted (this can happen if the
ppppmmmmllllooooggggggggeeeerrrr instance writing the log suddenly dies), then ppppmmmmllllooooggggmmmmeeeerrrrggggeeee will
detect and report the position of the corruption in the file, and any
subsequent information from that archive log will not be merged.
If any error is detected,
will exit with a non-zero status.
PPPPaaaaggggeeee 2222